chore(deps): update all dependencies #76
Open
+104
−40
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
7c2f7eb
to
4417064
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all
branch
5 times, most recently
from
61e2514
to
a18fb2b
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all
branch
9 times, most recently
from
0a8f29a
to
1cd9607
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
115cadc
to
33de24d
Compare
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
bot
force-pushed
the
renovate/all
branch
8 times, most recently
from
2eddaa5
to
7187fe1
Compare
renovate
bot
force-pushed
the
renovate/all
branch
11 times, most recently
from
56a4ee0
to
f86f5af
Compare
renovate
bot
force-pushed
the
renovate/all
branch
8 times, most recently
from
ee8c971
to
03da80d
Compare
renovate
bot
force-pushed
the
renovate/all
branch
9 times, most recently
from
d4825a9
to
77c8bba
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
77c8bba
to
4a8648b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.24.0->0.28.00.20.0->0.28.0v5->v6v2.2.0->v3.3.0v3.1.0->v3.3.0v0.34.0->v0.37.0v2.17.3->v2.21.0v1.33.1->v1.35.1v0.103.0->v0.113.0v0.2.0->v0.4.0v0.12.0->v0.13.0v2.22.8->v3.27.3v3.25.5->v3.27.31.22.3->1.23.31.22->1.239bf2ced->2d47cebv0.30.2->v0.31.2v0.30.2->v0.31.2v0.30.2->v0.31.20.71.2->0.74.2v0.18.4->v0.19.1Release Notes
aquasecurity/trivy-action (aquasecurity/trivy-action)
v0.28.0Compare Source
What's Changed
Full Changelog: aquasecurity/trivy-action@0.27.0...0.28.0
v0.27.0Compare Source
What's Changed
setup-trivyto install Trivy by @DmitriyLewen in https://github.com/aquasecurity/trivy-action/pull/406Full Changelog: aquasecurity/trivy-action@0.26.0...0.27.0
v0.26.0Compare Source
What's Changed
action/cachefor trivy databases by @DmitriyLewen in https://github.com/aquasecurity/trivy-action/pull/397Full Changelog: aquasecurity/trivy-action@0.25.0...0.26.0
v0.25.0Compare Source
What's Changed
New Contributors
Full Changelog: aquasecurity/trivy-action@0.24.0...0.25.0
docker/build-push-action (docker/build-push-action)
v6Compare Source
docker/login-action (docker/login-action)
v3.3.0Compare Source
Full Changelog: docker/login-action@v3.2.0...v3.3.0
v3.2.0Compare Source
Full Changelog: docker/login-action@v3.1.0...v3.2.0
v3.1.0Compare Source
Full Changelog: docker/login-action@v3.0.0...v3.1.0
v3.0.0Compare Source
Full Changelog: docker/login-action@v2.2.0...v3.0.0
cisco-open/operator-tools (github.com/cisco-open/operator-tools)
v0.37.0Compare Source
What's Changed
New Contributors
Full Changelog: cisco-open/operator-tools@v0.36.0...v0.37.0
v0.36.0Compare Source
What's Changed
New Contributors
Full Changelog: cisco-open/operator-tools@v0.35.0...v0.36.0
v0.35.0Compare Source
What's Changed
New Contributors
Full Changelog: cisco-open/operator-tools@v0.34.0...v0.35.0
onsi/ginkgo (github.com/onsi/ginkgo/v2)
v2.21.0Compare Source
2.21.0
Features
a69eb39]bcab9c8]Fixes
e548367]SpecsThatWillBeRunwithSpecsThatWillRun[
c2c4d3c]Maintenance
7e65a00]v2.20.2Compare Source
2.20.2
Require Go 1.22+
Maintenance
a671816]v2.20.1Compare Source
2.20.1
Fixes
d6f9640]v2.20.0Compare Source
2.20.0
Features
be5ab95]Maintenance
d303d14]7a50221]v2.19.1Compare Source
2.19.1
Fixes
63c8c30]ff41e27]Maintenance
76f4e0c]b69c00d]f097741]v2.19.0Compare Source
2.19.0
Features
Label Sets allow for more expressive and flexible label filtering.
v2.18.0Compare Source
2.18.0
Features
f010b65]d80eebe]Fixes
42013d6]Maintenance
fcf1fd7]8bb14fd]04bfad7]onsi/gomega (github.com/onsi/gomega)
v1.35.1Compare Source
1.35.1
Fixes
ca36da1]v1.35.0Compare Source
1.35.0
Features
EnforceDefaultTimeoutsWhenUsingContexts()to haveEventuallyhonor the default timeout when passed a context. (prior to this you had to expclility add a timeout) [e4c4265]StopTrying(message).Successfully()to abort aConsistentlyearly without failure [eeca931]Fixes
HaveFieldto avoid unexpected errors when used with async assertions. [3bdbc4e]Maintenance
a05a416]v1.34.2Compare Source
1.34.2
Require Go 1.22+
Maintenance
c59c6dc]8158b99]v1.34.1Compare Source
1.34.1
Maintenance
5e71dcd]v1.34.0Compare Source
1.34.0
Features
c549e0d]Fixes
878940c]ebadb67]Maintenance
8af2ece]123a071]0e69083]2675796]4160c0f]892c303]open-telemetry/opentelemetry-operator (github.com/open-telemetry/opentelemetry-operator)
v0.113.0Compare Source
0.113.0
💡 Enhancements 💡
operator: Programmatically create theServiceMonitorfor the operator metrics endpoint, ensuring correct namespace handling and dynamic configuration. (#3370)Previously, the
ServiceMonitorwas created statically from a manifest file, causing failures when theoperator was deployed in a non-default namespace. This enhancement ensures automatic adjustment of the
serverNameand seamless metrics scraping.collector: Create RBAC rules for the k8s_events receiver automatically. (#3420)collector: Inject environment K8S_NODE_NAME environment variable for the Kubelet Stats Receiver. (#2779)auto-instrumentation: add config for installing musl based auto-instrumentation for Python (#2264)auto-instrumentation: Supporthttp/jsonandhttp/protobufvia OTEL_EXPORTER_OTLP_PROTOCOL environment variable in addition to defaultgrpcfor exporting traces (#3412)target allocator: enables support for pulling scrape config and probe CRDs in the target allocator (#1842)🧰 Bug fixes 🧰
collector: Fix mutation of deployments, statefulsets, and daemonsets allowing to remove fields on update (#2947)Components
v0.112.0Compare Source
0.112.0
💡 Enhancements 💡
auto-instrumentation: Support configuring Java auto-instrumentation when runtime configuration is provided from configmap or secret. (#1814)This change allows users to configure JAVA_TOOL_OPTIONS in config map or secret when the name of the variable is defined in the pod spec.
The operator in this case set another JAVA_TOOL_OPTIONS that references the original value
e.g.
JAVA_TOOL_OPTIONS=$(JAVA_TOOL_OPTIONS) -javaagent:/otel-auto-instrumentation-java/javaagent.jar.auto-instrumentation: Adds VolumeClaimTemplate field to Instrumentation spec to enable user-definable ephemeral volumes for auto-instrumentation. (#3267)collector: Add support for persistentVolumeClaimRetentionPolicy field (#3305)auto-instrumentation: build musl based auto-instrumentation in Python docker image (#2264)auto-instrumentation: An empty line should come before the addition of Include ...opentemetry_agent.conf, as a protection measure against cases of httpd.conf w/o a blank last line (#3401)collector: Add automatic RBAC creation for thekubeletstatsreceiver. (#3155)auto-instrumentation: Add Nodejs auto-instrumentation image builds for linux/s390x,linux/ppc64le. (#3322)🧰 Bug fixes 🧰
target allocator: Permission check fixed for the serviceaccount of the target allocator (#3380)target allocator: Change docker image to run as non-root (#3378)Components
v0.111.0Compare Source
0.111.0
💡 Enhancements 💡
auto-instrumentation: set OTEL_LOGS_EXPORTER env var to otlp in python instrumentation (#3330)collector: Expose the Collector telemetry endpoint by default. (#3361)The collector v0.111.0 changes the default binding of the telemetry metrics endpoint from
0.0.0.0tolocalhost.To avoid any disruption we fallback to
0.0.0.0:{PORT}as default address.Details can be found here: opentelemetry-collector#11251
auto-instrumentation: Add support for specifying exporter TLS certificates in auto-instrumentation. (#3338)Now Instrumentation CR supports specifying TLS certificates for exporter:
otel-ca-bundle
present in otel-tls-certs
present in otel-tls-certs
v0.110.0Compare Source
0.110.0
🛑 Breaking changes 🛑
auto-instrumentation: Enable multi instrumentation by default. (#3090)Starting with this release, the OpenTelemetry Operator now enables multi-instrumentation by default.
This enhancement allows instrumentation of multiple containers in a pod with language-specific configurations.
Key Changes:
instrumentation.opentelemetry.io/container-namesannotation, instrumentation will be applied to the first container inthe pod spec by default. This only applies when single instrumentation injection is configured.
container(s) for instrumentation using language-specific annotations. Without this specification, the default behavior may
not work as expected for multi-container environments.
Compatibility:
instrumentation.opentelemetry.io/container-namesannotation do not need to take any action.Their existing setup will continue to function as before.
instrumentation.opentelemetry.io/container-namesand language-specific annotations(for multi-instrumentation) simultaneously will encounter an error, as this configuration is not supported.
collector: Remove ComponentUseLocalHostAsDefaultHost collector feature gate. (#3306)This change may break setups where receiver endpoints are not explicitly configured to listen on e.g. 0.0.0.0.
Change #3333 attempts to address this issue for a known set of components.
The operator performs the adjustment for the following receivers:
💡 Enhancements 💡
auto-instrumentation, collector: Add a must gather utility to help troubleshoot (#3149)The new utility is available as part of a new container image.
To use the image in a running OpenShift cluster, you need to run the following command:
See the README for more details.
collector: set default address for all parsed receivers (#3126)This feature is enabled by default. It can be disabled by specifying
--feature-gates=-operator.collector.default.config.operator: Use 0.0.0.0 as otlp receiver default address (#3126)collector: Add flag to disable components when operator runs on FIPS enabled cluster. (#3315)Flag
--fips-disabled-components=receiver.otlp,exporter.otlp,processor.batch,extension.oidccan be used to disablecomponents when operator runs on FIPS enabled cluster. The operator uses
/proc/sys/crypto/fips_enabledto checkif FIPS is enabled.
collector: Improves healthcheck parsing capabilities, allowing for future extensions to configure a healthcheck other than the v1 healthcheck extension. (#3184)auto-instrumentation: Add support for k8s labels such as app.kubernetes.io/name for resource attributes (#3112)You can opt-in as follows:
The following labels are supported:
app.kubernetes.io/namebecomesservice.nameapp.kubernetes.io/versionbecomesservice.versionapp.kubernetes.io/part-ofbecomesservice.namespaceapp.kubernetes.io/instancebecomesservice.instance.id🧰 Bug fixes 🧰
auto-instrumentation: Fix ApacheHttpd, Nginx and SDK injectors to honour their container-names annotations. (#3313)This is a breaking change if anyone is accidentally using the enablement flag with container names for these 3 injectors.
Components
Configuration
📅 Schedule: Branch creation - "before 4am" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.